Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @sentry/tracing from 7.68.0 to 7.69.0 #237

Closed
wants to merge 1 commit into from

Conversation

wkylin
Copy link
Owner

@wkylin wkylin commented Oct 8, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @sentry/tracing from 7.68.0 to 7.69.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 25 days ago, on 2023-09-13.
Release notes
Package name: @sentry/tracing
  • 7.69.0 - 2023-09-13

    Important Changes

    • New Performance APIs
      • feat: Update span performance API names (#8971)
      • feat(core): Introduce startSpanManual (#8913)

    This release introduces a new set of top level APIs for the Performance Monitoring SDKs. These aim to simplify creating spans and reduce the boilerplate needed for performance instrumentation. The three new methods introduced are Sentry.startSpan, Sentry.startInactiveSpan, and Sentry.startSpanManual. These methods are available in the browser and node SDKs.

    Sentry.startSpan wraps a callback in a span. The span is automatically finished when the callback returns. This is the recommended way to create spans.

    // Start a span that tracks the duration of expensiveFunction
    const result = Sentry.startSpan({ name: 'important function' }, () => {
    return expensiveFunction();
    });

    // You can also mutate the span wrapping the callback to set data or status
    Sentry.startSpan({ name: 'important function' }, (span) => {
    // span is undefined if performance monitoring is turned off or if
    // the span was not sampled. This is done to reduce overhead.
    span?.setData('version', '1.0.0');
    return expensiveFunction();
    });

    If you don't want the span to finish when the callback returns, use Sentry.startSpanManual to control when the span is finished. This is useful for event emitters or similar.

    // Start a span that tracks the duration of middleware
    function middleware(_req, res, next) {
      return Sentry.startSpanManual({ name: 'middleware' }, (span, finish) => {
        res.once('finish', () => {
          span?.setHttpStatus(res.status);
          finish();
        });
        return next();
      });
    }

    Sentry.startSpan and Sentry.startSpanManual create a span and make it active for the duration of the callback. Any spans created while this active span is running will be added as a child span to it. If you want to create a span without making it active, use Sentry.startInactiveSpan. This is useful for creating parallel spans that are not related to each other.

    const span1 = Sentry.startInactiveSpan({ name: 'span1' });

    someWork();

    const span2 = Sentry.startInactiveSpan({ name: 'span2' });

    moreWork();

    const span3 = Sentry.startInactiveSpan({ name: 'span3' });

    evenMoreWork();

    span1?.finish();
    span2?.finish();
    span3?.finish();

    Other Changes

    • feat(core): Export BeforeFinishCallback type (#8999)
    • build(eslint): Enforce that ts-expect-error is used (#8987)
    • feat(integration): Ensure LinkedErrors integration runs before all event processors (#8956)
    • feat(node-experimental): Keep breadcrumbs on transaction (#8967)
    • feat(redux): Add 'attachReduxState' option (#8953)
    • feat(remix): Accept org, project and url as args to upload script (#8985)
    • fix(utils): Prevent iterating over VueViewModel (#8981)
    • fix(utils): uuidv4 fix for cloudflare (#8968)
    • fix(core): Always use event message and exception values for ignoreErrors (#8986)
    • fix(nextjs): Add new potential location for Next.js request AsyncLocalStorage (#9006)
    • fix(node-experimental): Ensure we only create HTTP spans when outgoing (#8966)
    • fix(node-experimental): Ignore OPTIONS & HEAD requests (#9001)
    • fix(node-experimental): Ignore outgoing Sentry requests (#8994)
    • fix(node-experimental): Require parent span for pg spans (#8993)
    • fix(node-experimental): Use Sentry logger as Otel logger (#8960)
    • fix(node-otel): Refactor OTEL span reference cleanup (#9000)
    • fix(react): Switch to props in useRoutes (#8998)
    • fix(remix): Add glob to Remix SDK dependencies. (#8963)
    • fix(replay): Ensure handleRecordingEmit aborts when event is not added (#8938)
    • fix(replay): Fully stop & restart session when it expires (#8834)

    Work in this release contributed by @ Duncanxyz and @ malay44. Thank you for your contributions!

    Bundle size 📦

    Path Size
    @ sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 75.39 KB
    @ sentry/browser (incl. Tracing) - Webpack (gzipped) 31.32 KB
    @ sentry/browser - Webpack (gzipped) 21.92 KB
    @ sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 70.17 KB
    @ sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 28.51 KB
    @ sentry/browser - ES6 CDN Bundle (gzipped) 20.59 KB
    @ sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 221.8 KB
    @ sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 86.33 KB
    @ sentry/browser - ES6 CDN Bundle (minified & uncompressed) 61.18 KB
    @ sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 31.39 KB
    @ sentry/react (incl. Tracing, Replay) - Webpack (gzipped) 75.42 KB
    @ sentry/react - Webpack (gzipped) 21.95 KB
    @ sentry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 93.28 KB
    @ sentry/nextjs Client - Webpack (gzipped) 50.89 KB
  • 7.68.0 - 2023-09-06
    Read more
from @sentry/tracing GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@vercel
Copy link

vercel bot commented Oct 8, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
pro-react-admin ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 8, 2023 8:42pm

@sonarcloud
Copy link

sonarcloud bot commented Oct 8, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@wkylin wkylin closed this Oct 9, 2023
@wkylin wkylin deleted the snyk-upgrade-8972c2d14ec0b438832e6c9c9a7a0169 branch October 16, 2023 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants